System and method for providing automated receipt and bill collection, aggregation, and processing

ABSTRACT

A system and method in accordance with example embodiments may include automated receipt and bill collection, aggregation, and processing. Additionally, a system and method in accordance with example embodiments may a customer opt-in, scan one or more electronic messages including receipts and bills, retrieve transaction information from one or more electronic messages, associate retrieved transaction data with existing database data, and utilize the associated data to provide contextual information to a user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 61/769,839, filed on Feb. 27, 2013, the entire contents of which isincorporated herein by reference.

This application contains subject matter related to U.S. patentapplication Ser. No. 14/133,762, entitled “System and Method forTriggering Mobile Device Functionality Using a Payment Card, filed, Dec.19, 2013, the entire contents of which is incorporated herein byreference.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods for providingautomated electronic receipt, emailed receipt, bill, printed receipt,and/or e-receipt collection, aggregation, and processing.

BACKGROUND OF THE DISCLOSURE

Emailed receipts or “e-receipts” are sent by various, disparatemerchants to a customer's email address. E-receipts contain productlevel information. But the same product and/or service level informationis not provided to financial institutions during the transactionassociated with the e-receipt.

These and other drawbacks exist.

SUMMARY OF THE DISCLOSURE

Various example embodiments include systems and methods that includeautomated receipt and bill collection, aggregation, and processing.Additionally, a system and method in accordance with example embodimentsmay a customer opt-in, scan one or more electronic messages includingreceipts and bills, retrieve transaction information from one or moreelectronic messages, associate retrieved transaction data with existingdatabase data, and utilize the associated data to provide a message to auser.

An example system includes a database that stores customer information,the customer information including information about a customer emailaccount, one or more computer processors that accesses the customeremail account and retrieves transaction data from an electronic receiptincluded in an email in the customer email account, a collection modulethat collects the retrieved transaction data, and an association modulethat associates the retrieved transaction data with existing data in oneor more electronic databases.

An example method includes electronically scanning email of a customerin an email system to identify one or more emails that an electronicreceipt, electronically scanning the electronic receipts in the one ormore emails for transaction data associated with each of the respectiveelectronic receipts, using one or more computer processors to extractthe transaction data from the one or more electronic receipts, andassociating the extracted transaction data with data previously storedin one or more electronic databases.

A further example method includes scanning one or more electronic billsfor bill data, using one or more computer processors to extract the billdata from the one or more electronic bills, and associating theextracted bill data with data previously stored in one or moreelectronic databases.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present disclosure, together with furtherobjects and advantages, may best be understood by reference to thefollowing description taken in conjunction with the accompanyingdrawings, in the several Figures of which like reference numeralsidentify like elements, and in which:

FIG. 1 depicts an example embodiment of a system implementing automatede-receipt collection, aggregation, and processing;

FIG. 2 depicts an example embodiment of a system implementing automatede-receipt collection, aggregation, and processing;

FIG. 3 depicts an example embodiment of a system implementing automatede-receipt collection, aggregation, and processing; and

FIG. 4 depicts an example embodiment of a method utilizing automatede-receipt collection, aggregation, and processing;

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following description is intended to convey a thorough understandingof the embodiments described by providing a number of specific exampleembodiments and details involving systems and methods for providingautomated e-receipt collection, aggregation, and processing. It shouldbe appreciated, however, that the present disclosure is not limited tothese specific embodiments and details, which are exemplary only. It isfurther understood that one possessing ordinary skill in the art, inlight of known systems and methods, would appreciate the use of theinvention for its intended purposes and benefits in various embodiments,depending on specific design and other needs. A financial institutionand system supporting a financial institution are used as examples forthe disclosure. The disclosure is not intended to be limited tofinancial institutions only. Further, it is envisioned that theembodiments disclosed herein function with receipts, bills, or any othertype of financial documents. Receipts and bills are used below asexample embodiments but the system may function with other relevantdocuments as well.

According to the various embodiments of the present disclosure, systemsand methods enable automated e-receipt collection and processing. Theterm e-receipt as referred to herein may refer to any receipt that is inelectronic form, including, without limitation, emailed receipts,photographed receipts, scanned receipts. Automated e-receipt collection,aggregation, and processing may be utilized to provide detailed accounthistory and better marketing. The e-receipt collection and processingmay be automated using various systems and networks as described herein.

In an example embodiment, a retailer or other party may e-mail orotherwise transfer an electronic receipt to a user. For example, duringor after a purchase, a merchant may email a receipt or bill to an emailaddress designated by the user. A user may allow a financial institutionor other organization to scan an electronic mailbox, database, or otherrepository to find and process relevant receipts. The system may analyzereceipts to extract relevant information. As an example and not by wayof limitation, the system may analyze receipts to extract SKU (stockkeeping unit) level purchase data. This SKU level purchase data may beuseful to financial institutions or other organizations that may trackpurchase data of a user and present the data to the user in anappropriate context, such as in their statement. Additionally, a usermay send a receipt or bill for processing to an email address monitoredby the financial institution or other organization.

In an example embodiment, systems and methods may be utilized to processreceipt information. For example and not by way of limitation, aprocessing system may take SKU level purchase data and/or data thatdescribes a service and integrate the product and/or service data withknown transaction data, such as a user's bill or statement. In additionto presenting the data to the user in their statement, the combined datamay be used for analysis and other purposes, such as targeted offers orother marketing.

In an example embodiment, systems and methods may be utilized to permita user to photograph a printed receipt or bill. The systems and methodsmay analyze the photograph to extract relevant information, which may beadded to the system and made available to a user in similar ways ase-receipts or e-bills are utilized. Also, a user may send printeddocuments to a processing center for analysis and extraction ofinformation. Additionally, a user may optionally forward the photographto an e-mail address or other receiving system associated with a serviceprovider, so as to allow individual document analysis without grantingfull access to a user's inbox.

In an example embodiment, the user may benefit greatly from automatede-receipt collection and processing. For example and not by way oflimitation, the systems and methods may provide a mechanism for combinedview of purchase history across multiple merchants. More detailed datamay be available, and the user may be provided an option to “drill down”to the SKU level and the original receipt or bill. This may optionallybe achieved without requiring manual entry of purchases or iteminformation.

In an example embodiment, the combined view may be provided in thecontext of personal finance planning. For example and not by way oflimitation, there may be provided a table of frequently purchased items,charts regarding money spent on each item or category of items, spendingprojections, related items, or any other relevant information. Thecombined view may also provide a mechanism to scan credit card purchasesto detect fraud or errors.

In an example embodiment, the system may present offers, marketing,advertisements, coupons, and/or another item to a customer. For exampleand not by way of limitation, the system may present an advertisement toa similar or related product to one already purchased by a customer.Also, the system may allow a marketer or another party to present anoffer, marketing materials, or other information to a customer targetedbased on purchased products and/or services. An institution may utilizethe information to deliver the advertisement, offer, coupon, or othermessage to the customer. The institution may customize theadvertisement, offer, coupon, or other message according to theinformation. For example, and not by way of limitation, the institutionmay select, customize, or alter an advertisement, offer, coupon, orother message for relevance based on historical purchase patterns, orsegmentation of existing repeat customers, or integrate the informationwith additional forms of data for greater granularity (e.g.,geolocation, social graph). The offer, marketing materials, or otherinformation according to the information may be actionable by acustomer. For example and not by way of limitation, an institution maysend a user a discount offer on a given product and/or from a givenretailer. The user may then redeem the offer for the product and/or atthe retailer. The institution may deliver the offer, marketingmaterials, or other information to the customer.

In an example embodiment, a cardholder may opt-in to automated scanningof their e-mail inbox to search for e-receipts. Once opted in, aninstitution may check each incoming and/or existing e-mail for receipt,purchase, and/or other financial information. Upon finding relevantinformation, an institution may match the receipt against a credit cardtransaction or other institutional information. The institution mayparse the data to extract SKU or other product information to pair withthe transaction. By doing this, the institution may make the paired dataavailable to users and/or one or more third parties. The institution mayalso periodically scan the user's e-mail inbox for e-receipts. Theinstitution may use various algorithms for identifying the e-receipts,such as, for example, scanning the subject of the email for keywords(e.g., “receipt”, “e-receipt” or other like terms that may be used toidentify e-receipts) and/or known merchant names. The institution mayalso full text search the emails and use various algorithms to score theemails and determine whether the email is an e-receipt.

Upon processing of the information, the institution may optionallydisplay the information to a customer. For example and not by way oflimitation, the institution may provide an electronic financialstatement that shows financial, transactional, and credit information,but also displays, paired with that information, additional informationregarding the items, goods, and/or services that were the subject ofthat transaction. Also, the system may display receipts or billsassociated with transactions while the user is reviewing individualtransaction records, preferably on a service provider's web site orother information providing system. Permitting the display of associatedreceipts or other documents may reduce transaction dispute frequency byproviding additional information to a user.

In an example embodiment, the systems and methods provided herein mayautomatically process bills provided by a user. For example and not byway of limitation, the system may present an alert to a user when a billis received prompting the user to pay the bill instantly or schedule apayment for that bill (e.g. “We've received a bill fromUtilityCompanyInc. for $72.40. Pay now from Primary Checking (balance:$3212.45)?”) Additionally, alerts may be triggered based on billpatterns or amounts. An algorithm may be used to analyze the billingpatterns or amounts in order to determine spending behaviors or trends(e.g. “Your power bill is much higher this month than usual.”) This datacould be compared to aggregate data and presented to the user (e.g. “Youspend much more on clothing than others in your area.”)

FIG. 1 depicts an example system 100 for use with an e-receipt scanningsystem. System 100 may include one or more customers 102, one or more ofa third party 104, a network 106, and an institution 108.

One or more customers 102 may be in communication with the system 100.The one or more customers 102 may be, for example and not by way oflimitation, an individual or business with a credit card or bankingaccount with a bank or other financial institution. A customer may usethe credit card or banking account to consummate a number oftransactions with others. For example and not by way of limitation, acustomer may utilize a credit card, debit card or mobile payment deviceto purchase an item at a retailer.

A customer 104 may consummate a transaction with a third party 104. Thethird party 104 may be, for example and not by way of limitation, apurveyor of goods and services. The third party 104 may be a brick andmortar retail location, an individual performing services, an onlineretailer, a financial institution, or any other party. The third party104 may send or provide receipts to a customer. For example and not byway of limitation, the third party 104 may receive payment or otherwiseconsummate a transaction with a customer 102. The third party 104 maysend an e-receipt via e-mail, listing information about the transaction.For example and not by way of limitation, the information may includecustomer information, account information, transaction information,payment information, and/or information about the products, services, orother subject of the transaction (including but not limited to SKU,date, item descriptions, hourly rates, serial numbers, deviceidentifiers, or any other relevant information).

Network 106 may enable communication between an institution 108 and oneor more customers 102. For example, Network 106 may be one or more of awireless network, a wired network or any combination of wireless networkand wired network. For example, network 108 may include one or more of afiber optics network, a passive optical network, a cable network, anInternet network, a satellite network, a wireless LAN, a Global Systemfor Mobile Communication (“GSM”), a Personal Communication Service(“PCS”), a Personal Area Network (“PAN”), Wireless Application Protocol(WAP), Multimedia Messaging Service (MMS), Enhanced Messaging Service(EMS), Short Message Service (SMS), Time Division Multiplexing (TDM)based systems, Code Division Multiple Access (CDMA) based systems,D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b, 802.15.1, 802.11n and802.11g or any other wired or wireless network for transmitting andreceiving a data signal.

In addition, network 106 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (“WAN”), alocal area network (“LAN”), or a global network such as the Internet.Also network 106 may support an Internet network, a wirelesscommunication network, a cellular network, or the like, or anycombination thereof. Network 106 may further include one network, or anynumber of the exemplary types of networks mentioned above, operating asa stand-alone network or in cooperation with each other. Network 106 mayutilize one or more protocols of one or more network elements to whichthey are communicatively coupled. Network 106 may translate to or fromother protocols to one or more protocols of network devices. Althoughnetwork 106 is depicted as a single network, it should be appreciatedthat according to one or more embodiments, network 106 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Institution 108 may provide accounts for one or more customers 102. Inan example embodiment, the institution 108 may retrieve e-receipts fromthe electronic mail account of a customer 102 and extract data from thee-receipts. The institution 108 may store the extracted data in acustomer information database, and may optionally associate the datawith other portions of information, such as a line item on a statementfor presentation to the customer 102. Data may be stored in a formatsuch as, for example, a flat file, an indexed file, a hierarchicaldatabase, a post-relational database, a relational database, such as adatabase created and maintained with software from, for example Oracle®Corporation, Microsoft® Excel file, Microsoft® Access file, or any otherstorage mechanism.

FIG. 2 depicts an example system 200 for providing automated e-receiptcollection, aggregation, and processing. System 200 may includefinancial institution 202, network 204, merchant system 206, and emailsystem 208. In various embodiments, financial institution 203 may besimilar to institution 108 and/or system 300. Network 204 may be similarto network 106 and/or network 304.

In various embodiments, financial institution 202 also may includehardware and/or software that enables web scraping of, for example,email system 208. In various embodiments, financial institution 202 mayinclude, for example, an application programming interface (API) thatenables financial institution 202 to log in to, for example, emailsystem 208 as a customer of email system 208 and simulate emailbrowsing.

Merchant system 206 may include hardware and/or software that enables amerchant to prepare and transmit e-receipts. For example, merchantsystem 206 may include an email system similar to email system 208 thatallows a merchant to transmit e-receipts to merchant customers using,for example, email system 208. Merchant system 206 also may includehardware and/or software to transmit e-receipts via other messagingmethods, including, for example, SMS messaging, instant messaging,social network messaging, and the like.

Email system 208 may include hardware and/or software that enables, forexample, web-based email and/or post office protocol 3 (POP3) email.Email system 208 also may include Internet Message Access Protocol(IMAP) servers and/or Message Application Programming Interface (MAPI)servers. Email system 208 may maintain email accounts for a plurality ofaccount holders. An account holder may establish a username and passwordto enable the account holder to log in and access email messages. Invarious embodiments, email system 208 may allow account holders toreceive emails containing attachments, including e-receipts, and/oremails containing e-receipt information. Email system 208 may be coupledto network 204 to allow access to email system 208 by, for examplefinancial institution 202 and merchant 206.

FIG. 3 depicts an example system 300 that may enable a financialinstitution, for example, to provide network services to its customers.Example system 300 also may enable a merchant to transmit e-receipts tocustomers. System 300 also may depict the architecture of an exampleemail system. As shown in FIG. 3, system 300 may include a client device302, a network 304, a front-end controlled domain 306, a back-endcontrolled domain 312, and a backend 318. Front-end controlled domain306 may include one or more load balancers 308 and one or more webservers 310. Back-end controlled domain 312 may include one or more loadbalancers 314 and one or more application servers 316.

Client device 302 may be a network-enabled computer: As referred toherein, a network-enabled computer may include, but is not limited to:e.g., any computer device, or communications device including, e.g., aserver, a network appliance, a personal computer (PC), a workstation, amobile device, a phone, a handheld PC, a personal digital assistant(PDA), a thin client, a fat client, an Internet browser, or otherdevice. The one or more network-enabled computers of the example system300 may execute one or more software applications to enable, forexample, network communications.

Client device 302 also may be a mobile device: For example, a mobiledevice may include an iPhone, iPod, iPad from Apple® or any other mobiledevice running Apple's iOS operating system, any device running Google'sAndroid® operating system, including for example, Google's wearabledevice, Google Glass, any device running Microsoft's Windows® Mobileoperating system, and/or any other smartphone or like wearable mobiledevice.

Network 304 may be one or more of a wireless network, a wired network,or any combination of a wireless network and a wired network. Forexample, network 304 may include one or more of a fiber optics network,a passive optical network, a cable network, an Internet network, asatellite network, a wireless LAN, a Global System for MobileCommunication (GSM), a Personal Communication Service (PCS), a PersonalArea Networks, (PAN), D-AMPS, Wi-Fi, Fixed Wireless Data, IEEE 802.11b,802.15.1, 802.11n, and 802.11g or any other wired or wireless networkfor transmitting and receiving a data signal.

In addition, network 304 may include, without limitation, telephonelines, fiber optics, IEEE Ethernet 902.3, a wide area network (WAN), alocal area network (LAN) or a global network such as the Internet. Also,network 304 may support an Internet network, a wireless communicationnetwork, a cellular network, or the like, or any combination thereof.Network 304 may further include one network, or any number of exampletypes of networks mentioned above, operating as a stand-alone network orin cooperation with each other. Network 304 may utilize one or moreprotocols of one or more network elements to which they arecommunicatively couples. Network 304 may translate to or from otherprotocols to one or more protocols of network devices. Although network304 is depicted as a single network, it should be appreciated thataccording to one or more embodiments, network 304 may comprise aplurality of interconnected networks, such as, for example, theInternet, a service provider's network, a cable television network,corporate networks, and home networks.

Front-end controlled domain 306 may be implemented to to providesecurity for backend 318. Load balancer(s) 308 may distribute workloadsacross multiple computing resources, such as, for example computers, acomputer cluster, network links, central processing units or diskdrives. In various embodiments, load balancer(s) 310 may distributeworkloads across, for example, web server(S) 316 and/or backend 318systems. Load balancing aims to optimize resource use, maximizethroughput, minimize response time, and avoid overload of any one of theresources. Using multiple components with load balancing instead of asingle component may increase reliability through redundancy. Loadbalancing is usually provided by dedicated software or hardware, such asa multilayer switch or a Domain Name System (DNS) server process.

Load balancer(s) 308 may include software that monitoring the port whereexternal clients, such as, for example, client device 302, connect toaccess various services of a financial institution, for example. Loadbalancer(s) 308 may forward requests to one of the application servers316 and/or backend 318 servers, which may then reply to load balancer308. This may allow load balancer(s) 308 to reply to client device 302without client device 302 ever knowing about the internal separation offunctions. It also may prevent client devices from contacting backendservers directly, which may have security benefits by hiding thestructure of the internal network and preventing attacks on backend 318or unrelated services running on other ports, for example.

A variety of scheduling algorithms may be used by load balancer(s) 308to determine which backend server to send a request to. Simplealgorithms may include, for example, random choice or round robin. Loadbalancers 308 also may account for additional factors, such as aserver's reported load, recent response times, up/down status(determined by a monitoring poll of some kind), number of activeconnections, geographic location, capabilities, or how much traffic ithas recently been assigned.

Load balancers 308 may be implemented in hardware and/or software. Loadbalancer(s) 308 may implement numerous features, including, withoutlimitation: asymmetric loading; Priority activation: SSL Offload andAcceleration; Distributed Denial of Service (DDoS) attack protection;HTTP compression; TCP offloading; TCP buffering; direct server return;health checking; HTTP caching; content filtering; HTTP security;priority queuing; rate shaping; content-aware switching; clientauthentication; programmatic traffic manipulation; firewall; intrusionprevention systems.

Web server(s) 310 may include hardware (e.g., one or more computers)and/or software (e.g., one or more applications) that deliver webcontent that can be accessed by, for example a client device (e.g.,client device A 02) through a network (e.g., network 304), such as theInternet. In various examples, web servers, may deliver web pages,relating to, for example, online banking applications and the like, toclients (e.g., client device 302). Web server(s) 310 may use, forexample, a hypertext transfer protocol (HTTP or sHTTP) to communicatewith client device 302. The web pages delivered to client device mayinclude, for example, HTML documents, which may include images, stylesheets and scripts in addition to text content.

A user agent, such as, for example, a web browser, web crawler, ornative mobile application, may initiate communication by making arequest for a specific resource using HTTP and web server 310 mayrespond with the content of that resource or an error message if unableto do so. The resource may be, for example a file on stored on backend318. Web server(s) 310 also may enable or facilitate receiving contentfrom client device 302 so client device AO2 may be able to, for example,submit web forms, including uploading of files.

Web server(s) also may support server-side scripting using, for example,Active Server Pages (ASP), PHP, or other scripting languages.Accordingly, the behavior of web server(s) 310 can be scripted inseparate files, while the actual server software remains unchanged.

Load balancers 314 may be similar to load balancers 308 as describedabove.

Application server(s) 316 may include hardware and/or software that isdedicated to the efficient execution of procedures (e.g., programs,routines, scripts) for supporting its applied applications. Applicationserver(s) 316 may comprise one or more application server frameworks,including, for example, Java application servers (e.g., Java platform,Enterprise Edition (Java EE), the .NET framework from Microsoft®, PHPapplication servers, and the like). The various application serverframeworks may contain a comprehensive service layer model. Also,application server(s) 316 may act as a set of components accessible to,for example, a financial institution or other entity implementing system300, through an API defined by the platform itself. For Webapplications, these components may be performed in, for example, thesame running environment as web server(s) 310, and application servers316 may support the construction of dynamic pages. Application server(s)316 also may implement services, such as, for example, clustering,fail-over, and load-balancing. In various embodiments, where applicationserver(s) 316 are Java application servers, the web server(s) 316 maybehaves like an extended virtual machine for running applications,transparently handling connections to databases associated with backend318 on one side, and, connections to the Web client (e.g., client device302) on the other.

Backend 318 may include hardware and/or software that enables thebackend services of, for example, a financial institution or otherentity that maintains a distributes system similar to system 300. Forexample, backend 318 may include, a system of record, online bankingapplications, a rewards platform, a payments platform, a lendingplatform, including the various services associated with, for example,auto and home lending platforms, a statement processing platform, one ormore platforms that provide mobile services, one or more platforms thatprovide online services, a card provisioning platform, a general ledgersystem, and the like. Backend 318 may be associated with variousdatabases, including account databases that maintain, for example,customer account information, product databases that maintaininformation about products and services available to customers, contentdatabases that store content associated with, for example, a financialinstitution, and the like. Backend 318 also may include hardware and/orsoftware that enable automated e-receipt collection, aggregation, andprocessing. Backend 318 also may be associated with one or more serversthat enable the various services provided by merchant 206.

FIG. 4 provides an example method 400 for utilizing automated e-receiptcollection and processing. At step 402, the method may start. At step404, an institution may receive a customer opt-in from a customer. Theopt-in may include, for example and not by way of limitation,information permitting access to one or more electronic mail accounts,which may include log in information. The information permitting accessmay allow an institution to periodically log in to the customer's emailsystem, for example, as the customer and scan the customer's email thatis associated with the login information. The login information also maybe used by an application programming interface (API) associated withthe institution to have access to and scan the customer's email accountsas described herein. In various embodiments, the customer may opt-in viaa setting set by the customer in a settings profile associated with thecustomer. For example, a customer could log in to an online bankingapplication associated with the institution and set a setting in asetting profile associated with the customer. The settings profile alsomay allow the customer to provide the login information via, forexample, the online banking application. Once the institution hasreceived the opt-in, the institution may save a setting (e.g., a flag inan account associated with the customer) in an account database.

At step 406, an institution may scan electronic messages. In an exampleembodiment, the institution may, for example, log in as a customer toaccess customer email messages. To scan messages, in an exampleembodiment, the institution may step through each electronic mailmessage in a customer's inbox. Each message may be individually analyzedfor information indicating an e-receipt. As noted above, the method mayalso be utilized for bill analysis and processing. The scanningprocedure may include contextual analysis, keyword search, or any otherviable process. For example, the institution may search for the term“receipt” in each message to identify electronic receipts. The scanningprocedure also may include screen or web scraping of customer email.Also, the system may analyze portions of the message other than thebody, such as the subject, sender, date/time information, etc. Theinstitution may constantly and/or continuously monitor for new messages,scan at predetermined intervals, or scan as requested by a customer.

At step 408, the institution may retrieve transaction data from one ormore electronic messages. In an example embodiment, the institution mayextract transaction data from an e-mail that has been identified as areceipt, using, for example, techniques associated with web and/orscreen scraping. For example, the institution may retrieve the retailername, purchase price, and description of the item (including, but notlimited to, name and/or SKU level data). The institution may storetransaction data in, for example, databases associated with backendsystems of the institution.

At step 410, an institution may associate the transaction data retrievedfrom the electronic messages with existing data in a database. In anexample embodiment, the institution may maintain an electronic databasecontaining data related to a customer, such as, address, social securitynumber, income information, transaction information, demographicinformation, or any other information relevant to the system or method.For example, the institution may take the data retrieved from anelectronic receipt and find the transaction entry that represents thatpurchase. The institution may associate the retrieved data with thetransaction entry in one or more electronic databases. In variousembodiments, the institution may attempt to match information relatingto, for example, a purchase transaction with, for example informationreceived from an e-receipt. For example, the institution may attempt tocompare and match transaction amounts of purchase transactions with thetransaction amount from an e-receipt.

At step 412, the institution may provide a message to a user. For, themessage may be an offer, marketing communication, advertisement, coupon,and/or other message, and may optionally be a text, photo, or imagesection on an institution statement or web site. Also, the institutionmay record success rates of the messages. The institution may alsocollect analytics to store and/or provide to a third party. Theanalytics may include, for example, the success rates, the totaladvertisements presented, the timing and context of each ofadvertisement, and any other relevant information. For example,institution may monitor future transactions to determine whether anoffer has been redeemed as is described in U.S. patent application Ser.No. 14/133,762, entitled “System and Method for Triggering Mobile DeviceFunctionality Using a Payment Card, filed, Dec. 19, 2013, the entirecontents of which is incorporated by reference. At step 414, the methodmay end.

It is further noted that the systems and methods described herein may betangibly embodied in one of more physical media, such as, but notlimited to, a compact disc (CD), a digital versatile disc (DVD), afloppy disk, a hard drive, read only memory (ROM), random access memory(RAM), as well as other physical media capable of storing software, orcombinations thereof. Moreover, the figures illustrate variouscomponents (e.g., servers, computers, processors, etc.) separately. Thefunctions described as being performed at various components may beperformed at other components, and the various components bay becombined or separated. Other modifications also may be made.

In the preceding specification, various preferred embodiments have beendescribed with references to the accompanying drawings. It will,however, be evident that various modifications and changes may be madethereto, and additional embodiments may be implemented, withoutdeparting from the broader scope of the invention as set forth in theclaims that follow. The specification and drawings are accordingly to beregarded as an illustrative rather than restrictive sense.

1-20. (canceled)
 21. A system comprising: one or more processors runningan application programming interface (API); memory storing currenttransaction data, customer information, and one or more instructions,the customer information including log-in information for a customeremail account and the one or more instructions causing the one or moreprocessors to: receive a photographed transaction document comprising aphotograph of a printed receipt or a printed bill; log-in to thecustomer email account periodically and automatically, withoutinvolvement of the customer, using the log-in information; scan messagedata electronically, the message data corresponding to a first set ofone or more emails in the customer email account, to identify a secondset of one or more emails that include one or more electronictransaction documents; determine whether the photographed transactiondocument and each of the one or more electronic transaction documents isan electronic receipt or an electronic bill by: extracting transactiondata in the photographed transaction document or the electronictransaction document by: electronically scanning the photographedtransaction document or the electronic transaction document of acorresponding email of the second set of one or more emails; andperforming a contextual analysis of the corresponding email of thesecond set of one or more emails; and when the photographed transactiondocument or the electronic transaction document comprises an electronicreceipt: associating the extracted transaction data with the currenttransaction data; and determining that the extracted transaction data isassociated with a fraudulent transaction by determining that an errorexists between the current transaction data and the extractedtransaction data; or, when the photographed transaction document or theelectronic transaction document comprises an electronic bill: executingone or more bill actions, the one or more bill actions comprising (i)transmitting an alert to a user device associated with the user, thealert indicating that the electronic bill should be paid, and (ii)automatically scheduling payment of the electronic bill.
 22. The systemof claim 21, wherein the API provides access to a web scraper; andwherein the web scraper retrieves the transaction data from the one ormore electronic transaction documents included in the second set of oneor more emails.
 23. The system of claim 21, wherein the API providesaccess to the customer email account using the log-in information. 24.The system of claim 21, wherein the log-in information includes ausername and password.
 25. The system of claim 21, wherein the extractedtransaction data includes one or more extracted transaction amounts; andwherein the current transaction data includes one or more purchaseamounts.
 26. The system of claim 25, wherein the instructions furthercause the one or more processors to: compare the one or more extractedtransaction amounts with the one or more purchase amounts; and identify,based at least in part on the comparison, a particular purchasetransaction corresponding to the one or more electronic transactiondocuments.
 27. The system of claim 21, wherein the instructions furthercause the one or more processors to generate an output comprising: (i) afinancial planning tool associated with the extracted transaction dataand the current transaction data; (ii) an offer based on the extractedtransaction data and the current transaction data; and (iii) a purchasehistory associated with one or more merchants corresponding to one ormore merchants identified from the extracted transaction data.
 28. Thesystem of claim 27, wherein the offer comprises an advertisement for aproduct that is related to a previously purchased product.
 29. Thesystem of claim 27, wherein the financial planning tool comprisesspending projections.
 30. The system of claim 27, wherein the offercomprises a coupon based on historical purchase patterns.
 31. A methodcomprising: connecting, by one or more processors, a memory, a financialinstitute system, and an email system, the one or more processorsassociated with an application programming interface (API), the API toprovide access to an email browsing simulation on the email system;storing, in the memory, current transaction data and customerinformation, the customer information including log-in information for acustomer email account; receiving, at the one or more processors, aphotographed transaction document, the photographed transaction documentcomprising a photograph of a printed receipt or a printed bill;logging-in into the customer email account of the email system,periodically and automatically, without involvement of the customer,using the log-in information; scanning electronically, by the one ormore processors, message data corresponding to a first set of one ormore emails in the customer email account, to identify a second set ofone or more emails that include one or more electronic transactiondocuments; determining, by the one or more processors, whether thephotographed transaction document and each of the one or more electronictransaction documents is an electronic receipt or an electronic bill by:extracting, by the one or more processors, transaction data in thephotographed transaction document or the electronic transaction documentby: scanning electronically, by the one or more processors, thephotographed transaction document or the electronic transaction documentof a corresponding email of the second set of one or more emails; andperforming, by the one or more processors, a contextual analysis of thecorresponding email of the second set of one or more emails; and whenthe photographed transaction document or the electronic transactiondocument comprises an electronic receipt: associating, by the one ormore processors, the extracted transaction data with the currenttransaction data; and determining, by the one or more processors, thatthe extracted transaction data is associated with a fraudulenttransaction by determining that an error exists between the currenttransaction data and the extracted transaction data; or, when thephotographed transaction document or the electronic transaction documentcomprises an electronic bill: executing one or more bill actions, by theone or more processors, the one or more bill actions comprising (i)transmitting an alert to a user device associated with the user, thealert indicating that the electronic bill should be paid, and (ii)automatically scheduling payment of the electronic bill.
 32. The methodof claim 31, wherein the API provides access to a web scraper thatretrieves the transaction data from the one or more electronictransaction documents included in the second set of one or more emails.33. The method of claim 31, wherein the log-in information includes ausername and password.
 34. The method of claim 31, wherein the extractedtransaction data includes one or more extracted transaction amounts; andwherein the current transaction data includes one or more purchaseamounts.
 35. The method of claim 34, further comprising: comparing theone or more extracted transaction amounts with the one or more purchaseamounts; and identifying, based on the comparison, a particular purchasetransaction corresponding to the one or more electronic transactiondocuments.
 36. The method of claim 31, further comprising generating anoutput comprising: (i) a financial planning tool associated with theextracted transaction data and the current transaction data; (ii) anoffer based on the extracted transaction data and the currenttransaction data; and (iii) a purchase history associated with one ormore merchants corresponding to one or more merchants identified fromthe extracted transaction data.
 37. The method of claim 36, wherein thefinancial planning tool comprises a table of frequently purchased items.38. The method of claim 36, wherein the financial planning toolcomprises spending projections.
 39. The method of claim 36, wherein theoffer comprises an advertisement for a related product to one alreadypurchased.
 40. The method of claim 36, wherein the offer comprises acoupon based on historical purchase patterns.